#68 production dockerfiles builds pushing in ci #157
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-pushing-in-ci' into 68-production-dockerfiles-builds-pushing-in-ci
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
vygandas
changed the title
vygandas
added
github_actions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Builds docker image for api
Why is it needed?
We will want to deploy it
How to test it?
Well, it should work :) More or less boolean - either works or not
Extra details
For now it's in one large Docker image. Later, when it's clear how exactly it will be deployed and structured, we will create base image with base setup and maybe some different final images for workers and api.